src/components/Button/Button.tsx:234

• For the Link-rendering branch, aria-disabled/tabIndex don’t prevent mouse clicks, so a “disabled” Button with href will still navigate. Also disabled isn’t a valid attribute for anchors/Next Link. Consider omitting href when isDisabled is true, or add an onClick that calls preventDefault() (and maybe stopPropagation()) when disabled, while keeping styling via a data-attribute.
  src/components/ListingPhotosManager/ListingPhotosManager.tsx:173
• handleDrop builds newPhotos from the captured photos array after async compression/uploads. If photos are reordered/deleted while the upload is in flight, this can drop those updates. Prefer functional state updates (e.g., setPhotos(prev => [...prev, ...newFilenames])) and derive the value passed to onPhotosChange from that same update, or temporarily disable reordering/deletes while uploading.
  src/components/ListingPhotosManager/ListingPhotosManager.tsx:216
• In the delete error path, setPhotos(photos) reverts to the stale pre-delete array captured in the closure, which can overwrite legitimate changes that happened while the delete request was in flight (e.g., uploads/reordering). Consider restoring just the deleted filename (if missing) or tracking a snapshot in a ref, and/or disabling other photo mutations while deletingPhoto is set.
  src/components/EmailSelector/EmailSelector.tsx:124
• This introduces a non-translated UI string ("Copy failed") in a component that otherwise uses next-intl messages. Consider adding a Contact.copyButton.copyFailed (or similar) key in the locale message files and using t(...) here so non-English locales don’t show an English fallback.
  src/components/ProfileAccountSettings/ProfileAccountSettings.tsx:208
• Typo in function name: handleNewslettePreferenceUpdate (missing “r”). Renaming to handleNewsletterPreferenceUpdate will improve clarity and avoid propagating the typo to future references.

src/components/ProfileActions/ProfileActions.tsx:56

• handleSignOut wraps signOutAction() (which redirects) in a try/catch and swallows any thrown error. In Next.js, redirect() is implemented via a thrown redirect error; catching it can prevent the intended navigation and leave the UI stuck in a loading state. Consider removing the catch, or rethrowing redirect errors while only handling genuine failures (and/or switch to a <form action={signOutAction}> + SubmitButton pattern so the redirect/pending state is handled by the framework).
  src/components/ListingPhotosManager/ListingPhotosManager.tsx:198
• When an upload fails with a 413, the alert always uses the plural message even if the user only attempted a single file. Since files is in scope here, you can pick the singular vs plural message the same way you do for the preflight size check.
  src/components/ListingPhotosManager/ListingPhotosManager.tsx:228
• On delete failure, the UI restore appends the deleted photo to the end of the list ([...currentPhotos, photoToDelete]), which can change ordering compared to the pre-delete state. If ordering matters (and especially with drag-and-drop enabled), capture the original index (or previous array snapshot) before removing and restore it at the same position on failure.

src/components/Button/Button.tsx:37

• ButtonProps is currently defined as an intersection of both ButtonHTMLAttributes and AnchorHTMLAttributes. When href is provided, ...props is forwarded to StyledLink, which means button-only attributes (e.g. formAction, formMethod, name, etc.) are still type-allowed and can end up rendered on an <a> as invalid/meaningless attributes. Consider changing ButtonProps to a discriminated union based on href (or separate ButtonProps/LinkButtonProps) so TS prevents passing button-only props to link buttons (and vice versa), and so the spread onto <Link> can’t accidentally include form-only attributes.
  src/components/ListingWrite/ListingWrite.tsx:231
• For residential listings, the first-name update check compares profile.first_name !== name, but name can include transient whitespace while the value you actually send to updateFirstNameAction is validatedName (trimmed). This can trigger unnecessary update calls (and related UI states) when the only difference is whitespace. Consider basing the comparison on validatedName (or comparing trimmed values) so the update runs only when the persisted value would actually change.